Server and/or client device authentication

ABSTRACT

Embodiments of systems and methods for client and/or server authentication are provided. In one embodiment, a method includes sending information from a mobile network device to a server, wherein the information comprises a seed that is used by both the mobile network device and the server to compute a series of one time passwords. The method also includes receiving, by the mobile network device, a succession of one time passwords generated by the server throughout a session. And the method further includes comparing the received one time passwords generated by the server throughout the session to corresponding one time passwords generated at the mobile network device. In this manner, the server can be authenticated. In various embodiments, the process may be reversed to facilitate client, e.g., mobile network device, authentication.

RELATED APPLICATIONS

This application is a continuation of Ser. No. 14/887,219, filed Oct.19, 2015, which is a continuation of Ser. No. 14/175,115, filed Feb. 7,2014, now U.S. Pat. No. 9,197,634, which is a continuation of Ser. No.13/782,919, filed Mar. 1, 2013, now U.S. Pat. No. 8,656,459, which is acontinuation of Ser. No. 11/966,800, filed on Dec. 28, 2007, now U.S.Pat. No. 8,424,057, all of which are incorporated herein by reference intheir entirety.

TECHNICAL FIELD

The present invention relates generally to computer networking. Thepresent invention relates more particularly to an apparatus and methodfor inhibiting phishing on mobile network devices, such as cellulartelephones.

BACKGROUND

The use of cellular telephones and the like for accessing the Internetis becoming increasing popular. As wireless data transmission ratescontinue to increase, the practicality of accessing web pages via suchdevice improves.

The web pages accessed by such mobile network devices as cellulartelephones can be referred to mobile web pages. Mobile web pagestypically display less content as compared to their regular web pagecounterparts. This reduction in content is due in part to bandwidthconstraints and in part to the size of mobile displays.

One of the items commonly omitted from mobile web pages is a listing ofthe universal resource locator (URL) for the mobile web page presentlybeing viewed. Listing the URL of a web page presently being viewed isone way that users can prevent phishing.

Phishing is an illegitimate and often illegal attempt to obtain privateor sensitive information by deception over the Internet. For example,phishing can be used to obtain user names, account numbers, andpasswords for bank accounts, brokerage accounts, and the like. Thisdeception can occur by providing a fake web page that appears to be alegitimate web page. Users, who believe that the web page is itslegitimate counterpart, provide sensitive information to the web page.

For example, users may receive an email stating that they need tocontact their bank. The email can provide a link to the bank's website.Users that then contact the bank using the link provided in the emailare connected to a fake website for the bank instead of the officialwebsite for the bank. The fake website may look just as legitimate asthe bank's official website. The only apparent difference is the URL. Ifthe user doesn't notice the incorrect URL or if the URL is notdisplayed, then the user may enter sensitive information into a formthat is displayed on the fake web page.

The web pages of banks, brokerage firms, and the like typically requirethat a user enter a user name, account number, and password into a formto gain further access to the website. Entering this information intothe form of a fake web page provides this information to the personresponsible for the phishing.

As a further example, a user may visit a fraudulent merchant's website.This fraudulent website may allow the user to click on a link to awebsite for PayPal® or Google Checkout®. However, rather than taking theuser to the legitimate PayPal® or Google Checkout® website, the link onthe fraudulent merchant's website takes the user to a fake PayPal® orGoogle Checkout® website. At the fake PayPal® or Google Checkout®website, the user may enter sensitive information into a form that isdisplayed there, as discussed above.

Mobile network devices, such as cellular telephones, are particularlysusceptible to such deception because the URL is often not displayed asmentioned above. If the URL is displayed, such as is done on a desktopcomputer, the user can verify that the URL is correct for the web pagebeing displayed. However, since the URL is often not displayed oncellular telephone when visiting a website, the cellular telephone usermay not have an opportunity to verify that the URL is correct. Thecellular telephone user is thus undesirably vulnerable to phishing.

Thus, although such cellular telephones have proven generally suitablefor their intended purposes, they possess inherent deficiencies whichdetract from their overall effectiveness and desirability. Therefore, itis desirable to provide an apparatus and method for inhibiting phishingon mobile network devices, such as cellular telephones.

BRIEF SUMMARY

A method and system for inhibiting phishing is disclosed. According toan example of an embodiment, the method can comprise sending informationfrom a mobile network device to a website server, generating a one timepassword at the mobile network device from the information, generating aone time password at the website server from the information, sendingthe one time password generated at the website server to the mobilenetwork device when the mobile network device subsequently accesses thewebsite, and comparing the one time password generated at the websiteserver to the one time password generated at the mobile network device.

In this manner, the website can be authenticated. That is, it can bedetermined that the website actually being accessed is the website thatis intended to be accessed. Only the website that is intended to beaccessed will have the ability to generate a one time password that isthe same as the one generated by the mobile network device.

According to an example of an embodiment, the process described abovecan be reversed so as to facilitate client, e.g., mobile network device,authentication. Thus, a method for client authentication can comprisesending information from a website server to a mobile network device,generating a one time password at the website server from theinformation, generating a one time password at the mobile network devicefrom the information, sending the one time password generated at themobile network device to the website server when the mobile networkdevice subsequently accesses the website, and comparing the one timepassword generated at the mobile network device to the one time passwordgenerated at the website server so as to authenticate the mobile networkdevice.

According to an example of an embodiment, a mobile network device cancomprising a processor that is configured to send information from themobile network device to a website server, generate a one time passwordfrom the information, receive a one time password generated at thewebsite server when the mobile network device accesses the websiteserver, and compare the one time password generated at the websiteserver to the one time password generated at the mobile network device.

According to an example of an embodiment, a website server can comprisea processor configured to receive information from a mobile networkdevice generate a one time password from the information, and send theone time password to the mobile network device when the mobile networkdevice accesses the website.

Benefits include the mitigation of phishing when visiting website on theInternet.

This invention will be more fully understood in conjunction with thefollowing detailed description taken together with the followingdrawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a flowchart showing the computation of one time passwords bythe mobile network device and the website for use in authenticating thewebsite so as to mitigate phishing according to an example of anembodiment of the present invention;

FIG. 2 is a flowchart showing use of the one time passwords of FIG. 1 toauthenticate the website according to an example of an embodiment of thepresent invention;

FIG. 3 is a flowchart showing initial seeding of the one time passwordcomputation software according to an example of an embodiment of thepresent invention;

FIG. 4 is a flowchart showing initial seeding of the one time passwordcomputation software according to another example of an embodiment ofthe present invention; and

FIG. 5 is a block diagram showing communication of a mobile networkdevice and a personal computer with a website server according to anexample of an embodiment of the present invention.

Embodiments of the present invention and their advantages are bestunderstood by referring to the detailed description that follows. Itshould be appreciated that like reference numerals are used to identifylike elements illustrated in one or more of the figures.

DETAILED DESCRIPTION

A method and system for mitigating phishing are disclosed. Informationcan be exchanged between a mobile network device, such as a cellulartelephone, and a website server. This can be done during an initialcontact between the mobile network device and the website server. Thisinformation can define an initial seed that is used by both the mobilenetwork device and the website server to separately compute an identicalseries of one time passwords. Each time that the mobile network devicecontacts the website server, the website server sends the most recentone time password to the mobile network device. The mobile networkdevice can then compare this one time password to a one time passwordcomputed by the mobile network device to authenticate the websiteserver.

The website can continue to periodically generate one time passwords andsend them to the mobile networking device throughout the session. Themobile network device can continue to generate corresponding one timepasswords and compare them to the one time passwords provided by thewebsite, so as to maintain the integrity of the connection. For example,the website can periodically generate one time passwords and send themto the mobile networking device approximately every 1, 5, 10, 30, or 60seconds.

According to one example of an embodiment, the initial seeding of theone time password computation software can be done by having a user logonto a website with a mobile network device. The mobile network deviceregisters with the website. The website then sends a wirelessapplication protocol (WAP) push with cookie information to the mobilenetwork device.

According to one example of an embodiment, the initial seeding of theone time password computation software can be done by having the uservisit the website using an unregistered mobile network device. The userthen enters a user name and password for the first time. The websitesets a cookie to facilitate identification of the mobile network devicethe next time that the mobile network device contacts the website.

Examples of embodiments are discussed in further detail with referenceto the figures below.

Referring now to FIG. 1, an example of an embodiment of a system formitigating phishing comprises the use of one time password (OTP) orcertificate based software and/or hardware. Equivalent one time passwordcomputation systems must be used by both the mobile network device andthe website server. That is, both the mobile network device and thewebsite server must be capable of computing the same one time passwordwhen given the same seed. Of course, this can be accomplished if boththe mobile network device and the website server use identical one timepassword computation algorithms. It may also be accomplished via the useof different, but equivalent, algorithms.

As shown in FIG. 1, identical one time passwords are computer in boththe mobile network device and the website server. These passwords canthen be used to authenticate the website when the mobile network deviceaccesses the website.

More particularly, a token can be generated based upon a fingerprint ofthe mobile network device, as indicated in block 101. The fingerprintcan use information from the mobile network device. The fingerprint canuse information that is unique to the mobile network device. Forexample, the fingerprint can use information regarding one or morecookies that are present in the mobile network device, hypertexttransfer protocol (HTTP) header information that is present in themobile network device, and/or information that is manually entered bythe user. The HTTP can, for example, include the telephone number of themobile network device. Similarly, manually entered information caninclude the telephone number of the mobile network device. Thefingerprint can be any information that is representative of or relatedto the mobile network device. The information can be transformed ormanipulated in any desired manner. Indeed, the information itself can bethe fingerprint. The data size of the fingerprint can be larger,smaller, or the same as the data size of the information from which thefingerprint is generated.

A token can be generated from the fingerprint. The token can be formedby any desired means. For example, the token can be generated byencrypting the fingerprint. As a further example, the token can begenerated by forming a hash, such as a one way hash, from thefingerprint. The token can be any information that is represented of orrelated to the fingerprint. Indeed, the fingerprint or the informationfrom which the fingerprint is generated can be the token. The data sizeof the token can be larger, smaller, or the same as the data size of theinformation from which the token is generated.

A token can be distributed to the mobile device. The token can be eithera software token or a hardware token. The token can either include ornot include information derived from the mobile device (such asfingerprint information).

A token can be unique to a particular mobile network device. Suchuniqueness can be achieved by making the token dependent upon one ormore unique characteristics of the mobile network device. For example,the token can depend upon the telephone number of the mobile networkdevice.

A token can encapsulate a one time password. Thus, a token can eithercontain a one time password itself or can contain information that isused to generate a one time password. For example, a token can comprisea random number sequence that can be used, either alone or along withother information, as a seed for use in generating a one time password.

A one time password is computed from the token at the mobile device, asindicated in block 102. This one time password will be compared to a onetime password computed by the web sited server to authenticate thewebsite, as discussed below. This onetime password can be computedimmediately after the token is generated or upon a subsequent connectionto the website at which time authentication of the website is desired.

The token is sent from the mobile network device to the website, asindicated in block 103. If the token was distributed to the mobilenetwork device, the token does not need to be sent from the mobilenetwork device to the website. The token is used by the website serverto compute a one time password, as indicated in block 104. The samealgorithm for computing one time passwords can be used by both themobile network device and the website server. Thus, since both themobile network device and the website server are using the same seed,e.g., the token, to compute the one time passwords, the one timepassword computed by the mobile network device will be identical to theone time password computed by the website server.

Referring now to FIG. 2, the authentication process is shown accordingto an example of an embodiment. When a mobile network device accesses awebsite, then a one time password is sent from the website to the mobilenetwork device, as indicated in block 201. This one time password iscomputed from the seed provided by the mobile network device asdiscussed above. The same one time password has been computed by themobile network device, as also discussed above.

The one time password from the website is compared to the one timepassword of the mobile network device, as indicated in block 202. If theone time password from the website is the same as the one time passwordof the mobile network device, then use of the website can be authorized,as indicated in block 203.

Handshaking between the mobile network device and the website cancontinue throughout the session, as indicated in block 204. Suchhandshaking can comprise the periodic generation of the next one timepassword by the website and communication of that new one time passwordto the mobile network device. Each password received by the mobilenetwork device can be compared to a password generated by the mobilenetwork device.

As long the one time passwords in the series thereof that is generatedby the website server continue to match the onetime passwords generatedby the mobile network device, then the website can be consideredauthenticated and the session can continue. If a one time password fromthe website server does not match a corresponding one time passwordcomputed by the mobile network device, then the session can be halted.

Referring now to FIG. 3, an example of initially seeding the one timepassword computation software is shown. According to this example, auser logs onto a website with a personal computer (such as a desktop orlaptop personal computer), as shown in block 301. The personal computeris generally a device other than the mobile network device which isbeing registered and which will subsequently be used to access thewebsite. The mobile network device is registered with the website, asshown in block 302. The website then sends a wireless applicationprotocol (WAP) push with cookie information to the mobile networkdevice, as indicated in block 303. In this manner, the next time that auser visits the website, the one time password can be provided from thewebsite to the user.

Accessing a website is the initial process of contacting andestablishing communication with the website. Accessing a website occursprior to logging onto the website. Logging onto a website includes anauthentication process in which the user's authorization to gain furtheraccess to the website is verified. Authentication is typicallyaccomplished by requiring the user to provide a logon identification oruser name and a password.

Referring now to FIG. 4, another example of initially seeding the onetime password computation software is shown. According to this example,a user visits a website with an unregistered mobile network device, asindicated in block 401. The user then enters a user name and passwordfor the first time, as indicated in block 402. The website sets a cookiethat is used to identify the mobile network device the next time thatthe mobile network device contacts the website, as indicated in block403.

Referring now to FIG. 5, a mobile network device 501 can communicatewith a website server 502 via the Internet 504 to perform registrationand/or website authentication and access as described with reference toFIGS. 1, 2, and 4 above. A personal computer 503 can communicate withthe website server 502 via the Internet 504 to perform registration asdescribed with reference to FIG. 3 above.

Examples of mobile network devices can include cellular telephones,personal digital assistants, tablet computers, laptop computers, andnotebook computers. Mobile network devices can include any portabledevices that facilitate access to a network, such as the Internet.Embodiments can be used with mobile network devices that do not displaythe URL of a website being access, as well as with mobile network devicethat do display this URL.

Software and/or hardware for one time password generation can be asecure software application of the telephone and thus need not beseparately issued software and/or hardware. Thus, such software and/orhardware can be part of the mobile network device, such as part of theprocessor, firmware, and/or software thereof. Alternatively, suchsoftware and/or hardware can be added to the mobile network device bythe user or by someone else.

By authenticating a website prior to providing the website withsensitive information, the user can be better assured that the sensitiveinformation is being provided to a legitimate website. In this manner,phishing and the detrimental effects thereof can be mitigated.

The process described above can be reversed such that a client can beauthenticated by a website. That is, a token generated by the websitecan be sent to the mobile network device and then one or more one timepasswords can be generated by the mobile network device and communicatedto the website so as to authenticate the mobile network device. Thus,both the website and the client can authenticate one another, ifdesired.

Embodiments described above illustrate, but do not limit, the invention.It should also be understood that numerous modifications and variationsare possible in accordance with the principles of the present invention.Accordingly, the scope of the invention is defined only by the followingclaims.

The invention claimed is:
 1. A mobile network device comprising: anon-transitory memory storing passcode computation software; and one ormore hardware processors coupled to the non-transitory memory andconfigured to read the passcode computation software from the memory tocause the mobile network device to perform operations comprising:generating, from a token, a first mobile network device passcode at afirst time period during a computing session with a computing device;receiving, from the computing device, a corresponding first computingdevice passcode for the first time period; and extending the computingsession in response to the corresponding first computing device passcodematching the first mobile network device passcode at the first timeperiod.
 2. The mobile network device of claim 1, the operations furthercomprising: generating, from the token, a second mobile network devicepasscode at a second time period during the computing session, whereinthe second mobile network device passcode is different from the firstmobile network device passcode; receiving, from the computing device, acorresponding second computing device passcode for the second timeperiod; and extending the computing session in response to thecorresponding second computing device passcode matching the secondmobile network device passcode at the second time period.
 3. The mobilenetwork device of claim 1, the operations further comprising: haltingthe computing session in response to the corresponding first computingdevice passcode not matching the first mobile network device passcode atthe first time period.
 4. The mobile network device of claim 1, theoperations further comprising: receiving, prior to generating the firstmobile network device passcode, a cookie from the computing device. 5.The mobile network device of claim 4, wherein the token comprises thecookie.
 6. The mobile network device of claim 4, the operations furthercomprising: generating the token from the cookie and information uniqueto the mobile network device.
 7. The mobile network device of claim 1,the operations further comprising: repeating the generating, receiving,and extending in response to matching according to a time period betweenone second and sixty seconds.
 8. A method comprising: establishing, by aprocessor of a mobile computing device, a computing session having afirst time period with a computing device; receiving, by the mobilecomputing device from the computing device, a first computing devicepasscode at a first time during the first time period; matching, by themobile computing device, the received first computing device passcode toa second computing device passcode generated from a token; and extendingthe computing session to a second time period beyond the first timeperiod in response to the matching.
 9. The method of claim 8, furthercomprising: receiving, by the mobile computing device from the computingdevice, a third computing device passcode during the second time period;matching the received third computing device password to a fourthcomputing device password generated from the token; and extending thecomputing session beyond the second time period in response to matchingthe received third computing device password to the fourth computingdevice password.
 10. The method of claim 8, further comprising: haltingthe computing session in response to the received first computing devicepasscode not matching the second computing device passcode during thefirst time period.
 11. The method of claim 8, further comprising:receiving, electronically by the mobile computing device, a cookie fromthe computing device.
 12. The method of claim 11, wherein the tokencomprises the cookie.
 13. The method of claim 11, wherein the token isgenerated from the cookie and information unique to the mobile computingdevice.
 14. The method of claim 8, wherein the first time period isbetween one second and sixty seconds.
 15. A non-transitorymachine-readable medium having stored thereon machine-readableinstructions executable to cause a machine to perform operationscomprising: generating, from a token, a first mobile network devicepasscode during a first time period of a computing session with acomputing device; receiving, from the computing device, a correspondingfirst computing device passcode before the computing session ends; andextending the computing session beyond the first time period in responseto the corresponding first computing device passcode matching the firstmobile network device passcode.
 16. The non-transitory machine-readablemedium of claim 15, wherein the operations further comprise: generating,from the token, a second mobile network device passcode during a secondtime period of the extended computing session, wherein the second mobilenetwork device passcode is different from the first mobile networkdevice passcode; receiving, from the computing device, a correspondingsecond computing device passcode before the extended computing sessionends; and extending the extended computing session beyond the secondtime period in response to the corresponding second computing devicepasscode matching the second mobile network device passcode.
 17. Thenon-transitory machine-readable medium of claim 15, wherein theoperations further comprise: halting the computing session after thefirst time period in response to the corresponding first computingdevice passcode not matching the first mobile network device passcode.18. The non-transitory machine-readable medium of claim 15, wherein theoperations further comprise: receiving, prior to generating the firstmobile network device passcode, a cookie from the computing device. 19.The non-transitory machine-readable medium of claim 18, wherein theoperations further comprise: using the cookie as the token.
 20. Thenon-transitory machine-readable medium of claim 18, wherein theoperations further comprise: generating the token from the cookie andinformation unique to the machine.